<HTML><HEAD><TITLE>peer_queue_close(+Queue)</TITLE>
</HEAD><BODY>[ <A HREF="index.html">External Interface</A> | <A HREF="../../index.html">Reference Manual</A> | <A HREF="../../fullindex.html">Alphabetic Index</A> ]
<H1>peer_queue_close(+Queue)</H1>
Closes the peer queue Queue from ECLiPSe side.
<DL>
<DT><EM>Queue</EM></DT>
<DD>Peer queue (atom or integer)
</DD>
</DL>
<H2>Description</H2>
<P>
   Close the peer queue Queue from ECLiPSe side. When this predicate
   returns, the peer queue would be closed on both the ECLiPSe and remote
   sides, and book-keeping information on both sides updated to exclude the
   queue. As with creating a peer queue, closing a peer queue is performed
   explicitly from one side only. 

<P>
   The user should not close a peer queue with close/1. This will only
   close the ECLiPSe end of the queue, and would not remove the
   book-keeping information. Note that peer_queue_close/1 will still remove
   the book-keeping information if some of the underlying streams
   associated with the peer queue are already unexpectedly closed.
   
<H3>Modes and Determinism</H3><UL>
<LI>peer_queue_close(+) is semidet
</UL>
<H3>Fail Conditions</H3>
Queue is not a current peer queue.
<H3>Exceptions</H3>
<DL>
<DT><EM>(5) type error </EM>
<DD>Queue is not an atom or integer.
</DL>
<H2>See Also</H2>
<A HREF="../../kernel/externals/peer_queue_create-5.html">peer_queue_create / 5</A>, <A HREF="../../kernel/externals/peer_queue_get_property-3.html">peer_queue_get_property / 3</A>
</BODY></HTML>
